Refresh README and bump Malloy to 0.0.395#105
Closed
ofermend wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Ofer Mendelevitch <ofermend@gmail.com>
ofermend
force-pushed
the
pr/1-readme-and-malloy
branch
from
93e732c to
9f73bd1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@malloydata/*from0.0.244to0.0.395(package.json + regenerated lockfile; project version →0.0.394).GOOGLE_APPLICATION_CREDENTIALS, or legacyBIGQUERY_KEY), so contributors without GCP access can runnpm testand only see the DuckDB suite.code_of_conduct.md→CODE_OF_CONDUCT.mdso GitHub picks it up, and ignore generatedomop/data/.No notebook or sample
.malloyfiles were changed